Standard Data for Network Usage
Document Purpose
Provides standard data on network traffic and system resource usage when introducing SHIELD Gate in a customer's internal network environment.
This document can be used for purposes such as estimating the infrastructure capacity of the client company, reviewing implementation, and comparing with other solutions.
1. Measurement Overview
1.1 Measurement Environment
| item | Content |
|---|---|
| Measurement Environment | Cloud Virtualization Environment (8 Core, 32GB RAM) |
| Concurrent Users | 10 people |
| Measurement Site | Naver Maps, Naver Sports, general websites, video sites |
| Measurement Items | Network transmission and reception traffic, CPU usage, memory usage |
1.2 Measurement Scenarios
It was measured through the following three representative scenarios reflecting actual user behavior.
| Scenario | Usage Behavior | Traffic Characteristics |
|---|---|---|
| Scenario 1: General Web Surfing | Exploring News, Portals, and General Websites (Scrolling, Page Navigation) | Static Content Focus |
| Scenario 2: Map Site | Map scrolling, zoom in/out, place search | Dynamic Content + Tile Image |
| Scenario 3: Video Playback | HD Video Streaming | Continuous Streaming Traffic |
1.3 Precautions for Using Measurement Results
⚠️ This data isStandard Measurement Environment Reference Valuesand, in actual customer environments, differences may occur due to the following factors.
- User-specific usage patterns (page dwell time, video viewing ratio, etc.)
- Types of Content on the Accessed Site (Static Pages vs Dynamic Pages)
- Video Playback Quality Settings (HD/FHD/UHD, etc.)
- Network Environment (Bandwidth, Latency)
- Frame Rate Settings (12fps / 24fps / Auto)
2. Network Usage by Scenario (Based on 10 Concurrent Connections)
2.1 Scenario 1: General Web Browsing
| Measurement Items | Measurement value |
|---|---|
| Network Average | 75.18 Mbps |
| n Reception (RX, User PC Direction) | 80.23 Mbps |
| n Transmission (TX, towards RBI server) | 70.12 Mbps |
| Pod CPU Usage | 0.99 cores |
| Node CPU Usage | 3.09 cores |
💡 General web surfing experiences a concentration of traffic at the moment of page loading, with little to no traffic occurring during the page stay.
2.2 Scenario 2: Map Site (Naver Map)
| Measurement Items | Measurement value |
|---|---|
| Network Average | 32.70 Mbps |
| n Reception (RX) | 35.11 Mbps |
| N Transmission (TX) | 30.29 Mbps |
| Pod CPU Usage | 1.22 cores |
| Node CPU Usage | 4.15 cores |
💡 Map sites load tile images when scrolling or zooming, but the average traffic is lower compared to videos. However, the frequency of user interactions is high, resulting in higher CPU usage than regular web browsing.
2.3 Scenario 3: Video Playback
| Measurement Items | Measurement value |
|---|---|
| Network Average | 50.05 Mbps |
| n Reception (RX) | 60.80 Mbps |
| N Transmission (TX) | 39.30 Mbps |
| Pod CPU Usage | 2.12 cores |
| Node CPU Usage | 6.03 cores |
💡 Video playback involves continuous screen updates, resulting in the highest measurements for both traffic and CPU usage. There may be additional fluctuations depending on the video quality (SD/HD/FHD).
3. Per Capita Conversion Figures (For Infrastructure Capacity Estimation)
the measurement values of the above scenarioBased on one userThis is the value converted to __PH_0__. You can use it when estimating network bandwidth based on the number of concurrent users.
3.1 Per Person Usage by Scenario
| Scenario | Network Average (Per Person) | Receiving (RX) | Transmission (TX) | Pod CPU (per person) |
|---|---|---|---|---|
| General Web Surfing | Approximately 7.5 Mbps | about 8.0 Mbps | Approximately 7.0 Mbps | about 0.10 cores |
| Map Site | Approximately 3.3 Mbps | Approximately 3.5 Mbps | About 3.0 Mbps | about 0.12 cores |
| Video Playback | About 5.0 Mbps | Approximately 6.1 Mbps | Approximately 3.9 Mbps | about 0.21 cores |
3.2 Expected Traffic by Number of Concurrent Users (Based on Video Playback)
Video playback is the scenario with the highest traffic,Conservative Criteria for Infrastructure Capacity Estimationcan be utilized.
| Number of simultaneous users | Expected Network Average | Recommended bandwidth (30% margin) |
|---|---|---|
| 10 people | about 50 Mbps | about 65 Mbps |
| 50 people | about 250 Mbps | About 325 Mbps |
| 100 people | about 500 Mbps | Approximately 650 Mbps |
| 200 people | Approximately 1.0 Gbps | Approximately 1.3 Gbps |
| 500 people | Approximately 2.5 Gbps | Approximately 3.3 Gbps |
💡 Recommended Bandwidthis the value with an additional 30% margin over the measured values to respond to peak traffic and network fluctuations. In real environments, the average value may be lower depending on user usage patterns.
3.3 Recommended Calculation of General Usage Environment (Mixed Scenario)
In a real work environment, general web browsing is predominant, so the following mixing ratio standards are recommended.
| Usage Patterns | ratio | Average Traffic Per Person |
|---|---|---|
| General Web Surfing | 70% | 7.5 Mbps × 0.7 = 5.25 Mbps |
| Map/Search and Other Interactions | 20% | 3.3 Mbps × 0.2 = 0.66 Mbps |
| Video Playback | 10% | 5.0 Mbps × 0.1 = 0.50 Mbps |
| Mixed Average (Per Capita) | Approximately 6.4 Mbps |
| Number of simultaneous users | Expected Traffic for Mixed Patterns |
|---|---|
| 10 people | about 64 Mbps |
| 50 people | About 320 Mbps |
| 100 people | About 640 Mbps |
| 200 people | Approximately 1.3 Gbps |
| 500 people | Approximately 3.2 Gbps |
💡 This mixing ratio is based on a typical office environment, and adjustments may be necessary according to the actual work characteristics of the client company.
4. CPU/Memory Resource Usage
4.1 System Resources by Scenario
| Scenario | Total Pod CPU | Total Node CPU | Pod CPU per person |
|---|---|---|---|
| General Web Surfing | 0.99 cores | 3.09 cores | about 0.10 cores |
| Map Site | 1.22 cores | 4.15 cores | about 0.12 cores |
| Video Playback | 2.12 cores | 6.03 cores | about 0.21 cores |
4.2 Resource Impact of Frame Rate Settings
The CPU usage varies depending on the screen transmission frame rate settings. You can choose according to the usability requirements of the client company.
| Frame Settings | CPU Usage (based on 2 people) | Memory Usage | Usability |
|---|---|---|---|
| 12 fps | Approximately 1.5 cores (38~40%) | About 1,000 Mi | Sufficient for general work use |
| 24 fps | Approximately 1.7 cores (44~50%) | About 1,000 Mi | Smooth Screen Motion |
| Auto | Approximately 1.8 cores (46~50%) | About 1,000 Mi | Automatically Adjust Based on Content |
💡 A higher frame rate improves perceived quality for users, but it also increases CPU usage. In a typical work environment, 12fps provides sufficient usability.
5. Frequently Asked Questions (FAQ)
Q1. In what environment was this measurement obtained?
A. Measured based on 10 simultaneous connections in a cloud virtualization environment (8 Core, 32GB RAM). Actual figures may vary depending on the network bandwidth and usage patterns of the client's internal network environment.
Q2. How is traffic calculated when there are N people?
A. It can be simply calculated by multiplying the average traffic per person by the number of concurrent users. However, it is recommended to add a 30% buffer for peak time response. (See section 3.2)
Q3. Should the video scenario be assessed even in environments where the video playback ratio is low?
A. In a typical office environment, it is more practical to use the mixed scenario criteria from Section 3.3. The video scenario criteria areConservative EstimationPlease make use of the poem.
Q4. What is the reason for the different traffic ratios between transmission (TX) and reception (RX)?
A. In the RBI environment, the user PC receives screen dataReceivingThe proportion of doing is higher (RX > TX). Transmission mainly corresponds to the sending of mouse/keyboard events.